Markdown linter and link checker jobs#216
Conversation
Make sense. Let's wait for your PR to merge, and then I will rework the touched files. |
|
Sorry, this needs to resolve conflicts coming with merge of #215 |
Merged your changes and applied the formatting rules on them. Please review |
Resolved |
jreineckearm
left a comment
jreineckearm
left a comment
There was a problem hiding this comment.
Thanks for making the changes and taking care of the initial conversion!
I'd lie if I'd say I understand all the config files yet. But I trust your knowledge here. :-)
Good to merge as far as I am concerned. But we may want to wait for @KeilChris to lift his change request.
KeilChris
left a comment
KeilChris
left a comment
There was a problem hiding this comment.
We must preserve the four spaces before sub-bulletpoints, otherwise the documentation build will create unexpected results.
jreineckearm
left a comment
jreineckearm
left a comment
There was a problem hiding this comment.
LGTM! CI seems happy now
3 participants
Changes
The goal is to ensure that all changes to Markdown files follow consistent formatting standards and that any URLs included are valid and reachable. If any issues are detected, the workflow will fail and provide detailed output, highlighting the exact lines with errors along with clear error messages.